<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
 <head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  <title>PKCS7 Flags/Constants</title>

 </head>
 <body><div class="manualnavbar" style="text-align: center;">
 <div class="prev" style="text-align: left; float: left;"><a href="openssl.key-types.html">Key types</a></div>
 <div class="next" style="text-align: right; float: right;"><a href="openssl.signature-algos.html">Signature Algorithms</a></div>
 <div class="up"><a href="openssl.constants.html">预定义常量</a></div>
 <div class="home"><a href="index.html">PHP Manual</a></div>
</div><hr /><div id="openssl.pkcs7.flags" class="section">
   <h2 class="title"><acronym>PKCS7</acronym> Flags/Constants</h2>
   <p class="para">
    The S/MIME functions make use of flags which are specified using a
    bitfield which can include one or more of the following values:
    <table class="doctable table">
     <caption><strong><acronym>PKCS7</acronym> CONSTANTS</strong></caption>
      
       <thead>
        <tr>
         <th>Constant</th>
         <th>Description</th>
        </tr>

       </thead>

       <tbody class="tbody">
        <tr id="constant.pkcs7-text">
         <td><strong><code>PKCS7_TEXT</code></strong></td>
         <td>Adds text/plain content type headers to encrypted/signed
         message. If decrypting or verifying, it strips those headers from
         the output - if the decrypted or verified message is not of MIME type
         text/plain then an error will occur.</td>
        </tr>

        <tr id="constant.pkcs7-binary">
         <td><strong><code>PKCS7_BINARY</code></strong></td>
         <td>Normally the input message is converted to &quot;canonical&quot; format
         which is effectively using <em>CR</em> and <em>LF</em>
          as end of line: as required by the S/MIME specification.  When this
          option is present, no translation occurs. This is useful when
          handling binary data which may not be in MIME format.</td>
        </tr>

        <tr id="constant.pkcs7-nointern">
         <td><strong><code>PKCS7_NOINTERN</code></strong></td>
         <td>When verifying a message, certificates (if
           any) included in the message are normally searched for the
           signing certificate. With this option only the
           certificates specified in the <em><code class="parameter">extracerts</code></em>
           parameter of <span class="function"><a href="function.openssl-pkcs7-verify.html" class="function">openssl_pkcs7_verify()</a></span> are
           used.  The supplied certificates can still be used as
           untrusted CAs however.
         </td>
        </tr>

        <tr id="constant.pkcs7-noverify">
         <td><strong><code>PKCS7_NOVERIFY</code></strong></td>
         <td>Do not verify the signers certificate of a signed
         message.</td>
        </tr>

        <tr id="constant.pkcs7-nochain">
         <td><strong><code>PKCS7_NOCHAIN</code></strong></td>
         <td>Do not chain verification of signers certificates: that is
         don&#039;t use the certificates in the signed message as untrusted CAs.
         </td>
        </tr>

        <tr id="constant.pkcs7-nocerts">
         <td><strong><code>PKCS7_NOCERTS</code></strong></td>
         <td>When signing a message the signer&#039;s certificate is normally
         included - with this option it is excluded.  This will reduce the
         size of the signed message but the verifier must have a copy of the
         signers certificate available locally (passed using the
         <em><code class="parameter">extracerts</code></em> to
         <span class="function"><a href="function.openssl-pkcs7-verify.html" class="function">openssl_pkcs7_verify()</a></span> for example).
         </td>
        </tr>

        <tr id="constant.pkcs7-noattr">
         <td><strong><code>PKCS7_NOATTR</code></strong></td>
         <td>Normally when a message is signed, a set of attributes are
         included which include the signing time and the supported symmetric
         algorithms.  With this option they are not included.
         </td>
        </tr>

        <tr id="constant.pkcs7-detached">
         <td><strong><code>PKCS7_DETACHED</code></strong></td>
         <td>When signing a message, use cleartext signing with the MIME
         type <em>&quot;multipart/signed&quot;</em>. This is the default
         if you do not specify any <em><code class="parameter">flags</code></em> to
         <span class="function"><a href="function.openssl-pkcs7-sign.html" class="function">openssl_pkcs7_sign()</a></span>.
         If you turn this option off, the message will be signed using
         opaque signing, which is more resistant to translation by mail relays
         but cannot be read by mail agents that do not support S/MIME.</td>
        </tr>

        <tr id="constant.pkcs7-nosigs">
         <td><strong><code>PKCS7_NOSIGS</code></strong></td>
         <td>Don&#039;t try and verify the signatures on a message</td>
        </tr>

       </tbody>
      
     </table>

   </p>
   <blockquote class="note"><p><strong class="note">Note</strong>: 
     <p class="para">These constants were added in 4.0.6.</p>
   </p></blockquote>
  </div><hr /><div class="manualnavbar" style="text-align: center;">
 <div class="prev" style="text-align: left; float: left;"><a href="openssl.key-types.html">Key types</a></div>
 <div class="next" style="text-align: right; float: right;"><a href="openssl.signature-algos.html">Signature Algorithms</a></div>
 <div class="up"><a href="openssl.constants.html">预定义常量</a></div>
 <div class="home"><a href="index.html">PHP Manual</a></div>
</div></body></html>
